Skip to content

Fix v3 config loading for Jiti re-exports#1

Closed
Dunqing wants to merge 6 commits intomainfrom
fix/issue-431-jiti
Closed

Fix v3 config loading for Jiti re-exports#1
Dunqing wants to merge 6 commits intomainfrom
fix/issue-431-jiti

Conversation

@Dunqing
Copy link
Copy Markdown
Owner

@Dunqing Dunqing commented Feb 5, 2026

Fixes stack overflow when v3 config re-exports a workspace package loaded via Jiti by switching v3 config loading to Jiti import. Adds fixture to cover the re-export path.

Dunqing and others added 6 commits February 5, 2026 19:15
* Remove unused deps

* Use the plugin that has already been imported rather than dynamically importing it again
… importing it again (tailwindlabs#442)

* Use the plugin that has already been imported rather than dynamically importing it again

* Skip visiting non-node children
- Add knip devDependency and lint script
- Remove unused devDependencies: @microsoft/api-extractor, cpy-cli, resolve-from, rimraf
- Update copy-licenses.js exclude list

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
- Add oxlint and oxlint-tsgolint for type-aware linting
- Configure .oxlintrc.json to disable noisy rules
- Update lint script to run oxlint on src and tests

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
@Dunqing Dunqing closed this Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants